Manually upgrading the SIEM, EDLP, and Log Agents

Depending on your OS and the type of package that you want to install, perform the steps in the following sections to upgrade the on-premises connectors manually. This manual upgrade procedure is applicable for EDLP, SIEM, and Log Agent.

For CentOS and RHEL

If you installed the rpm package in the previous version, upgrade the connector using an RPM package. For instructions, see the Upgrading a connector using an RPM package section.

Upgrading a connector using an RPM package 

  1. From the Management Console, go to Administration > System Settings > Downloads.

  2.  Click the download icon for the On-premise Connector rpm package.

Graphical user interface, application Description automatically generated

  1. Copy the downloaded RPM package to the Node Server on which you want to install.

  2. Log in to the Node Server.

  3. Stop the Node Server services:

    sudo service node-server stop

  1. Run the following command:

    sudo yum install epel-release

  1. Run the following command to upgrade the connector:

    sudo yum upgrade ./enterprise-connector*.rpm

  1. Start the Node server services:

    sudo service node-server start

For Ubuntu

If your previous connector was installed using a Tar package, to get the latest connector version, you can either perform a fresh installation using a Debian package (Method 1) or upgrade the connector using a Tar package (Method 2).

If your previous connector was installed using a Debian package, you can upgrade the connector using a Debian package (Method 3).

Method 1 (Recommended): Installing the latest connector version using a Debian package

If your previous connector was installed using a Tar package, to get the latest connector version, you can perform a fresh installation of the latest connector version using a Debian package. Detailed steps for this procedure are provided below.

Pros:

  • You can use service/systemctl commands to start/stop the services.

  • Additional dependencies required for other features are automatically installed by the apt command.

 

Cons:

  • As this is a fresh installation, you are required to run install.sh script.

  • Provide the details such as nodeName, authToken etc, during the installation.


Method 2: Upgrading a connector using a Tar package

Pros:

  • No need to run the install.sh script again.

Cons:

  • You need to use the sudo bash <script> command for any start/stop operations.

  • Before untarring the TAR package in the opt/ciphercloud directory, you need to delete the old boot-ec-*.jar file.

Method 3: Upgrading a connector using a Debian package

 

Use this procedure if your previous connector was installed using a Debian package.

Method 1: Installing the latest connector version using a Debian package

Note: If you have already installed any connector on your machine using a Tar package, stop the Node Server services and delete the ciphercloud directory located under the opt directory before starting this procedure.

  1. From the Management Console, go to Administration > System Settings > Downloads.

  2.  Click the download icon for the On-premise Connector - Debian package.

  1. Copy the downloaded Debian package to the Node Server on which you want to install. 

  2. Log in to the Node server.

  3. Run the following command to start the installation in the Linux instance: 

    [ubuntu@localhost home]# sudo apt install ./enterprise-connector_<version>_amd64.deb

    Where <version> is the current DEB file version in the Management Console. 

    Note: Make sure you are connected to the internet while performing this installation.

  1. Click Yes when prompted to save the IPv4 and IPv6 rules.

  2. Run the following command to change to the directory in which to install the connector. 

    cd /opt/ciphercloud/node-server 

  1. Run the following command to configure the installation options.

    ./install.sh 

    System response:

    Initializing node-server install script. Please wait..

  1. Respond to the system prompts as follows:

    Please enter Management Server endpoint 

    [wss://nm.<domain>:443/nodeManagement]:

  1. Enter the default option shown or enter the URL for this installation.

  2. Management Server endpoint: <Node Management endpoint URL> 

  3. Enter the unique ID for this tenant.

    Input Tenant Id: <tenant name>

  1. Enter the unique name for the Node Server.

    Input Node Server Unique Name: <node_name>

  1.  Enter the API token (click the API Token button in the Configuration tab)

    Input Node Server Token: <Node API token>

    Once Node server installation is done. Start node server using ‘sudo service node-server start’.

  1. Select Y to install with upstream proxy and enter the upstream proxy details.

    Note If you do not want to use the upstream proxy, specify N and press Enter.

    Does upstream proxy exist? [y/n]: y

    Input Host Name of upstream proxy server: 192.168.222.147 

    Input port number of upstream proxy server: 3128

  1. Enter the username and password if you want to enable the upstream proxy with authorization. Otherwise, press Enter. 

    Input upstream proxy authorization - user name (Press enter key if no authorization required): test

    Input upstream proxy authorization - password: test@12763

  1. Run the following command to start the Node Server:

    sudo service node-server start 

Method 2: Upgrading a connector using a Tar package 

Note: If you are on the Ubuntu OS, we recommend that you install the latest Debian package. For instructions, see Installing a new connector with Debian package.

  1. From the Management Console, go to Administration > System Settings > Downloads.

  2. Click the download icon for the On-premise Connector Tar Package.

  3. Copy the downloaded Tar package to the Node Server on which you want to upgrade.

  4. Log in to the Node Server.

  5. Stop the Node Server services using the following command:

    sudo bash /opt/ciphercloud/node-server/bin/agent/agent stop

  1. Make a backup copy of the boot-ec-*.jar file and save it to a different location.

  2. Delete the boot-ec-verion.jar file from the /opt/ciphercloud/node-server/lib directory.

  3. Untar the On-premise Connector Tar package to /opt/ciphercloud:

    sudo tar -xvf enterprise-connector-<version>.tar.gz –directory /opt/ciphercloud

    sudo chown -R ccns:ccns /opt/ciphercloud/node-server

    This action extracts the contents to the node-server directory. 

  1. Start the Node Server services:

    sudo bash /opt/ciphercloud/node-server/bin/agent/agent start

Method 3: Upgrading a connector using a Debian package

If your previous connector on the Ubuntu OS was installed using a Debian package, use this procedure for upgrading your connector.

  1. From the Management Console, go to Administration > System Settings > Downloads.

  2.  Click the download icon for the On-premise Connector - Debian package.

  1. Copy the downloaded Debian package to the Node Server on which you want to install.

  2. Log in to the Node Server.

  3. Stop the Node Server services:

    sudo service node-server stop

  1. Run the following command to upgrade the connector:

    sudo apt upgrade ./enterprise-connector*.deb

  1. Click Yes when prompted to save the IPv4 and IPv6 rules.

  2. Start the Node Server services:

    sudo service node-server start